During this week I created and or edited the following sections of the document in addition to editing and formatting the work submitted to me by the team.
Due to the nature of this project and the design document used we have thus far been using the event-oriented and outside-in design methodologies. These design methods seem to fit the project best based on the clients and programmers needs and the requirements document provided. Due to the lack of a conceptual design needed for the client the design document is to be primarily utilized by the programming team. The event-oriented decomposition fits well in this situation because the page formats have been well defined by the client so the main design task is to spell out how certain events change the state of these pages. This also allows work to be started on the general (high level) states while requirements gathers information needed for a more detailed design , whereas modular decomposition may not. Outside-in design is similar to event-oriented decomposition in that it allows the design team to work with the inputs and outputs to the system without immediately considering the specifics of what the system does with this data.
| Items |
| Complete Detailed Design |
| Revise Document |
| Items |
| Is the User's Evaluation of the system stored any where? |
| Date | Name | Revision |
| 11-8-01 | Brent Job | Created Table of contents, Design approach, and inserted architecture. |
| 11-19-01 | Brent Job | Inserted user interaction, data storage, and implementation platform sections |
| 11-26-01 | Brent Job | Minor changes to all existing sections. Add the external system interface section. |
(Note: this diagram was later thrown out)
5.2 Guest Login Page
5.3 Passages Page
5.4 Questions Page
5.5 Instructions Page
5.6 Information Page
5.7 Calculations Page
5.8 Reading Results Page
5.9 Reading Tips Page
5.10 Evaluation Page